Mobile device enabled tiered data exchange via a vehicle

ABSTRACT

A mobile device enabled tiered data exchange via a vehicle is disclosed. A mobile device can access profile information related to a tiered-data sharing profile. The tiered-data sharing profile can associate data with a sharing tier designating security, privacy, or authorization constraints on sharing the associated data. A sharing tier can further designate obfuscation of the data as a constraint on sharing the data. The mobile device can enable access to the data subject to the constraints of the tiered-data sharing profile. In an embodiment, tiered data can be shared from the mobile device to an external service device via vehicle device. In another embodiment, tiered data can be shared from the mobile device to a service device of the vehicle.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of, and claims priority to each of,U.S. patent application Ser. No. 14/927,461 (now U.S. Pat. No.10,021,105), filed on 29 Oct. 2015, and entitled “MOBILE DEVICE ENABLEDTIERED DATA EXCHANGE VIA A VEHICLE,” which is a continuation of U.S.patent application Ser. No. 14/075,784, filed on 8 Nov. 2013, now issuedas U.S. Pat. No. 9,203,843, and entitled “MOBILE DEVICE ENABLED TIEREDDATA EXCHANGE VIA A VEHICLE,” the entireties of which applications arehereby incorporated by reference herein.

TECHNICAL FIELD

The disclosed subject matter relates to adaptation of a vehicle relatedto tiered data exchange via a mobile device.

BACKGROUND

By way of brief background, modern vehicles can include adaptablesubsystems. These adaptable subsystems can facilitate adaptation of thevehicle to improve usability of the vehicle. As an example, mobiledevices can include an identifier allowing a vehicle to adjust seats topreset conditions associated with the identifier, allowing a vehicle toadjust radio station settings to a set associated with the identifier,etc. Further, some mobile devices can be used directly as transpondersto interface with systems external to a vehicle, e.g., tollbooths, tollin motion, etc., allowing a mobile device inside a vehicle to interactwith said external systems.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is an illustration of a system that facilitates employing amobile device enabled tiered data exchange for vehicle adaptation inaccordance with aspects of the subject disclosure.

FIG. 2 is a depiction of a system that facilitates employing a mobiledevice, receiving external tiered data, enabling tiered data exchangefor vehicle adaptation in accordance with aspects of the subjectdisclosure.

FIG. 3 illustrates a system that facilitates employing a mobile deviceenabled tiered data exchange for vehicle adaptation and data tokens inaccordance with aspects of the subject disclosure.

FIG. 4 illustrates a system that facilitates employing a mobile deviceenabled tiered data exchange for vehicle adaptation and communication ofa data token from a token store device to an external service device inaccordance with aspects of the subject disclosure.

FIG. 5 illustrates a system that employs a mobile device enabledtiered-data exchange for vehicle adaptation and an external dataprovider in accordance with aspects of the subject disclosure.

FIG. 6 illustrates a method facilitating employing a mobile deviceenabled tiered data exchange for vehicle adaptation in accordance withaspects of the subject disclosure.

FIG. 7 depicts a method facilitating employing a mobile device enabledtiered data exchange for vehicle adaptation comprising authorization viathe mobile device in accordance with aspects of the subject disclosure.

FIG. 8 illustrates a method facilitating employing a mobile deviceenabled tiered data exchange for vehicle adaptation and data tokens inaccordance with aspects of the subject disclosure.

FIG. 9 depicts a schematic block diagram of a computing environment withwhich the disclosed subject matter can interact.

FIG. 10 illustrates a block diagram of a computing system operable toexecute the disclosed systems and methods in accordance with anembodiment.

DETAILED DESCRIPTION

The subject disclosure is now described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding of the subject disclosure. It may be evident, however,that the subject disclosure may be practiced without these specificdetails. In other instances, well-known structures and devices are shownin block diagram form in order to facilitate describing the subjectdisclosure.

Conventional vehicles can employ many manually adjustable systems, suchas, radio stations, seat adjustments, pedal position adjustments,climate control settings, etc. Some newer vehicles have advancedadjustment systems that can store settings for adjustable vehiclesubsystems, e.g., storing sets of seat adjustments that can allow theseat to adjust several parameters at the touch of a single button. Insome instances, these stored vehicle subsystem adjustments can beactivated by items such as computerized keys, key fobs, etc., e.g., whena computerized key is inserted in the ignition, the vehicle canautomatically adjust the seat based on settings associated with theparticular key inserted in the ignition.

Further, some newer vehicles can be associated with information sharingdevices. These data sharing devices can share data wirelessly, visually,or audibly. As an example, a toll transponder can comprise a radiofrequency identification (RFID) device, a Wi-Fi or BLUETOOTH device,etc. As another example, a parking pass device can comprise a displaythat displays an image that can comprise a barcode, quick response (QR)code or other type of multi-dimensional code, a letter and/or numbercode, a code comprising symbols, etc., that can enable a reader tovisually capture the displayed image to verify that the associatedvehicle is permitted to park at that parking facility, or to charge anaccount associated with the image to pay for parking at that parkingfacility. In another example, an audio transponder can generate an audiocode that can effect payment or verification of permission to use aservice. However, conventionally, these information sharing devices canbe typically preconfigured by a user associated with the vehicle or byan organization associate with a service relating to the sharing device.As an example, a toll transponder for a particular bridge crossing canbe programmed by the toll authority before being given to a user toplace in their vehicle. As such, these types of information sharingdevices can be associated with a limited number of uses, e.g., a tolltransponder may not be able to be programmed with parking passinformation, thus causing a user to carry a second information sharingdevice where parking pass service is also needed. Further, these devicescan lack security features, for example, where a toll pass transponderis stolen, it can often be used by the thief because it can lack userauthentication.

Additionally, these conventional systems can be generally strongly tiedto individual vehicles or drivers. As an example, in most conventionalsystems, a computerized key fob can be associated with a seat adjustmentfor a first vehicle, however the same key fob would not typically causeseat adjustment in a second vehicle. As such, a driver who has aprogrammed seat adjustment associated with a key fob for her personalvehicle would not generally be able to rent another vehicle, even of thesame make and model, and expect the programmed seat adjustment to workin the rented vehicle based on the presence of the key fob. Similarly,for example, a parking pass display for a first user will often beassociated with the user's account and a second user could not use thesame parking pass display for a second user account. As another example,rental vehicles can include toll transponders that bill the rental caragency and then the rental car agency bills the customer for tollscharged to the rental car agency. Where an information sharing devicecan be adapted to display information related to particular individuals,users, or profiles, a single information display device in a rentalvehicle could display information such that the relevant user is chargedfor tolls directly rather than via the rental car agency. This canimprove the privacy of the renter because the rental car agency does nothave a list of toll charges incurred by the renter. Similarly, where adriver owns several vehicles, conventional systems would not generallyallow an information sharing device of each vehicle to share informationto services relevant to the particular user of that vehicle. Moreover,as car sharing services become increasingly popular, information sharingdevices that can interact with internal or external services based onthe particular vehicle user can present opportunities for monetizationof services, improved privacy, improved security of data, and areduction in the number of information sharing devices needed to provideaccess to multiple external or internal services.

In comparison to conventional systems, sharing of data with a vehicleinformation sharing device via a mobile device, in accord with theinstant specification, can facilitate access to driver or passengersharing profile information. This access to driver or passenger sharingprofile information can be employed to enable adaptation of the vehicleinformation sharing device. A mobile device can enable adaptation of avehicle based information sharing devices across vehicles, unliketypical systems, allowing a user, e.g., a driver or passenger, to carrysharable data with them into whatever vehicle they are associated within real time, e.g., a rental car, a friend's car, a shared car, a bus, avanpool, etc. As an example, a user can have a toll transponder account,a parking pass account credit, and a bank account associated with a datasharing profile. This user can then access the data sharing profile viaa mobile device such that when they drive to work in the morning, avehicle information sharing device can be updated with the data for thedata sharing profile allowing the vehicle information sharing device toeffect payment of a freeway toll on the drive in, allow access to theparking garage as they arrive at work, and pay for energy from theirbank account as they recharge their vehicle in the garage during theday. Further, when the user goes borrows a friend's truck to run anerrand, the truck information sharing device can be updated with theuser data from the profile such that additional freeway tolls are chargeto the user account rather than to the truck owner's account. Similarly,where the user borrows their spouse's vehicle the following day to go towork, the spouse's vehicle information sharing device can be updatedwith the user's data so that the user's accounts are charged for tolls,parking, etc. Then when a user flies to another city for business, whenthe user rents a vehicle at the airport, that vehicle informationsharing device can be updated with the user's data enabling the user topurchase in-vehicle services such as in-vehicle GPS, satellite radio,etc. Moreover, as the user drives around in the other city, their bankaccount can be charged for external services such as tolls, parking, carwashes, etc., via the vehicle information sharing system.

In an aspect, some data can be treated with different levels of securityor privacy protections to give the user a sense of safety in using adata sharing profile with a vehicle information sharing device. As such,data can be classified in different tiers, each associated with adefined level of privacy and security. Tiered data can comprise dataassociated with a determined level of data security. This dataassociated with a determined level of data security can be shared data.Further, this data associated with a determined level of data securitycan be included in profile information related to sharing the data. Asan example, a first tier can include openly shared data, for example,radio station preset stations, seat adjustment position information,speed alert preferences, etc., that may not be associated with anysecurity or authorization protocol and that can be shared with anyvehicle the mobile device is associated with. As another example, asecond tier can include more sensitive data that can be associated withan authorization to share, this more sensitive data could include a QRcode for entrance to a parking garage, an RF code for a garage dooropener, etc., such that once the authorization to share has beenreceived, the vehicle information sharing device can be given theinformation for use. The more sensitive data could also be associatedwith rules for use, expiration times, geofencing parameters, expirationproximities, etc., so that, for example, the authorization can be validso long as the user does not move the mobile device more than 100 feetfrom the vehicle for more than 10 hours, allowing the user to keep theauthorization in the vehicle while she is at work, asleep at home, etc.,but the authorization expires if she goes on vacation and leaves the carat home, etc. Further, where the user hops in a friend's vehicle, thedata would not be shared without authorization. As a further example,highly sensitive data can be associated with a third tier that shares atoken representation of the data rather than the data itself, such assharing a token allowing payment for parking from a bank account withoutsharing the bank account information itself with the external parkingservice. These tokens can be exchanged, for example, via areconciliation service provider, with the mobile service provider, witha bank, etc. The tokens can also be associated with rules, such asexpiration conditions, time limits, value limits, secondaryauthorization, etc., so that, for example, a token can be shared withthe vehicle information sharing device allowing the information sharingdevice to pay for vehicle recharging for three days. The token can thenbe shared, via the vehicle information sharing device, with an externalvehicle recharging service for three days without exposing the actualbank account information with the vehicle recharging service. It will benoted that numerous other tiers can be employed and that each tier canbe associated with rules relating to the security, privacy, and sharingof the data associated with that tier.

Sharing of tiered data with the vehicle information sharing device canbe by wired or wireless links. In an aspect, a mobile device can sharetiered data with vehicle information sharing device by cellular, Wi-Fi,BLUETOOTH, NFC, ZIGBEE, etc. Similarly, a mobile device can share tiereddata with vehicle information sharing device by USB cable, FIREWIREcable, etc. Sharing of tiered data can be subject to rules orauthorization. In an aspect, authorization can be performed on themobile device, e.g., by password, fingerprint, voice command, iris scan,etc. Similarly, authorization can be performed via the vehicle orvehicle information sharing device, e.g., a password can be entered intoa vehicle user interface, etc. Further, authorization can comprise otheruser interfaces, e.g., a web based profile can be set to enable accessto certain data or tiers of data, the user can then enter a passwordinto the vehicle user interface, and then the vehicle can query themobile device for approval, whereby the user can approve the request forthe data on the mobile device user interface. It will be appreciatedthat nearly any mechanism for authentication or authorization can beemployed without departing from the scope of the instant disclosure.

In an aspect, a mobile device can enable a vehicle information sharingdevice to access tiered data by way of tiered-data sharing profileinformation. Tiered-data sharing profile information can be stored onthe mobile device, stored external to the mobile device, or both.Similarly, tiered data can be stored on the device, external to themobile device, or both. Moreover, tiered data shared with a vehicleinformation sharing device can be stored on the vehicle informationsharing device. In an embodiment, tiered data shared with the vehicleinformation sharing device is not stored on the vehicle informationsharing device and only shared via the vehicle information sharingdevice as a conduit. This can improve security and privacy of tiereddata shared via the vehicle. For example, where the vehicle informationsharing system does not have a local copy of the tiered data, the tiereddata is not resident should the vehicle be stolen in an attempt to hackinto the vehicle information sharing device to recover tiered data. Inan embodiment, tiered data can be cached in a volatile memory of thevehicle information sharing device so that it is only resident while thevehicle information sharing device is powered on, thereby reducing datatransmission but still providing some security for the data by notkeeping tiered data in a non-volatile memory of the vehicle informationsharing device.

In an embodiment, a mobile device can perform operations comprisingreceiving profile information related to sharing data associated with adetermined level of data security and receiving vehicle informationrelated to a vehicle. Based on the profile information and the vehicleinformation, the mobile device can determine signal information relatedto sharing content information with a service device in accord with aconstraint associated with the determined level of data security.Further, the mobile device can facilitate access to the signalinformation for a device of the vehicle to enable sharing of the contentinformation with the service device.

In another embodiment, a method can comprise receiving profileinformation associated with a user identity, data, and a determinedlevel of data security for the data. The method can further comprise themobile device receiving vehicle information related to a vehicle. Basedon receiving an approval input, the mobile device of the method canassociate the profile information with the vehicle. Further, based onthe profile information and the vehicle information, the method cancomprise determining, by the mobile device, content information relatedto account data associated with the user identity, wherein the contentinformation is accessible to a service device in response to aconstraint associated with the determined level of data security beingdetermined to be satisfied. The method can also comprise the mobiledevice facilitating access to the content information for a device ofthe vehicle to enable sharing of the content information with theservice device.

Moreover, in further embodiment, a computer readable storage device cancause a mobile device to profile information associated with an identityof a subscriber, a set of information, and a determined level ofinformation security for information of the set of information. Thesystem can further receive vehicle information. Based on a constraintassociated with the determined level of information security, the systemcan determine content information related to account informationassociated with the identity, wherein the content information issharable with a service device. The system can also facilitate sharingof the content information, based on the vehicle information, to theservice device via a device of the vehicle.

To the accomplishment of the foregoing and related ends, the disclosedsubject matter, then, comprises one or more of the features hereinaftermore fully described. The following description and the annexed drawingsset forth in detail certain illustrative aspects of the subject matter.However, these aspects are indicative of but a few of the various waysin which the principles of the subject matter can be employed. Otheraspects, advantages and novel features of the disclosed subject matterwill become apparent from the following detailed description whenconsidered in conjunction with the provided drawings.

FIG. 1 is an illustration of a system 100, which facilitates employing amobile device enabled tiered data exchange for vehicle adaptation inaccordance with aspects of the subject disclosure. System 100 caninclude mobile device 110. Mobile device 110 can be a smartphone, tabletcomputer, laptop computer, or any other type of mobile device.

Mobile device 110 can comprise user interface (UI) component 112. UIcomponent 112 can receive an indication from a user of mobile device110. The indication can be related to sharing tiered data with avehicle, e.g., a vehicle information sharing device (not illustrated) ofthe vehicle. Nearly any vehicle subsystem can be subject to adaptationor control based on information related to shared tiered data. As anexample, headlights can be adapted to flash codes that can be used topay a toll fee, a stereo system can be adapted to play an audio code topay the toll fee, a visually readable display can be adapted to displaya scannable bar code, a vehicle BLUETOOTH transceiver can be adapted totransmit a signal to effect payment of the toll fee, etc. Further, avehicle can comprise a dedicated tiered data sharing device to sharedata that can effect payment of the toll fee. As such, for clarity andbrevity, sharing tiered data via a vehicle can be discussed in terms ofemploying a ‘vehicle information sharing device’, which term can be readto comprise a dedicated device(s) and/or any other vehicle subsystem,unless explicitly stated to the contrary. Further, as stated herein, avehicle information sharing device can share information with aninternal and/or external service by way of RF, images, light energy(including infrared signals), audio tones, etc. With this in mind, itwill be noted that a vehicle can employ more than one subsystem to shareinformation, e.g., flashing headlights, audio tones on the stereo, andRF codes from a BLUETOOTH adapter, to share information with one or moreinternal or external services based on information related to atiered-data sharing profile.

In an aspect, UI component 112 can be employed to implementauthorization or approval related to sharing tiered data with a vehicle,e.g., a vehicle information sharing device. As an example, UI component112 can receive a password, fingerprint, voice print, iris scan, etc. aspart of authorizing sharing of tiered-data with the vehicle.

In another aspect, UI component 112 can be employed to directly inputtiered data into mobile device 110. This can populate a tiered-datasharing profile. The profile can be stored on the device or external tothe device, e.g., on a server by uploading the tiered data input and/orprofile to the server. A tiered-data sharing profile can also be createdexternal to the mobile device and can be received by the device astiered-data sharing profile information 120. A tiered-data sharingprofile can comprise data to be shared, the data associated with a levelor tier of sharing associated with security rules, privacy rules,authorization rules, etc. As an example, the tiered-data sharing profilecan include a bank account number associated with a high sensitivitytier. This high sensitivity tier can be, for example, associated withsharing a digital token of data, hereinafter a token, rather than thedata itself, an authorization rule requiring a user to input afingerprint on a mobile device, a rule indicating that the token isvalid for 4 hours, a rule that the token is valid for use in adesignated geographic area only, etc. As such, when a battery chargingstation, to charge a battery of the vehicle, requests a payment from thevehicle by transmitting an RF signal to the vehicle, the vehicleaffiliated with the tiered-data sharing profile can then verify that amobile device associated with the tiered-data sharing profile is withinthe designated geographic area. The vehicle can then request fingerprintauthorization via the mobile device. The fingerprint can be received byway of UI component 112 of mobile device 110. Next, the vehicle canshare a token with the battery charging service. The token can beredeemed by a reconciling system of the battery charging service up to 4hours after the token is issued. Redemption of the token results infunds being paid to the charging service corresponding to funds beingwithdrawn from the bank account identified in the tiered-data sharingprofile without sharing the bank account number with the chargingservice. Tokens can employ nearly any technique enabling improvedsecurity, privacy, or usability in comparison to not using suchtechniques. Examples of such techniques can include federation, OAUTH,root certificate based validation, online validation, etc., that canfacilitate desirable token traits, such as non-repudiability,non-reusability, etc.

Vehicle information from vehicle 130 can be received by mobile device110. Vehicle information from vehicle 130 can be received via a wired orwireless link between the vehicle and mobile device 110. Vehicleinformation from vehicle 130 can comprise identification information,parameter information, subsystems information, vehicle informationsharing device information, etc. Vehicle information from vehicle 130can enable mobile device 110 to associate a vehicle with tiered-datasharing profile information 120. In an embodiment, vehicle informationfrom vehicle 130 can be from a vehicle in close proximity to mobiledevice 110, e.g., where mobile device 110 is within the vehicle. Vehicleinformation from vehicle 130 can be used to request authentication ofthe vehicle from a user associated with a tiered-data sharing profile,such as by presenting information about the vehicle to the user via UIcomponent 112 and requesting that the user approve associating thevehicle, e.g., vehicle information sharing device, with the tiered-datasharing profile of the user. In an embodiment, this association canpersist such that a user does not need to approve a vehicle each timethey get in it. In another embodiment, the association can benon-persistent, such that the user is always asked to authorize avehicle. Further embodiments can include association persistence rules.These rules can, for example, persist some vehicle associations and notothers, can persist a vehicle association for a determined time, persista vehicle association so long as a determined number of new associationshave not been created, etc. As such, a user could designate rules that,for example, cause his personal car to have a persistent associationuntil he has associated with two other vehicles or the association ismore than 3 months old.

Mobile device 110 can enable access to tiered-data shared to vehicle132. Mobile device 110 can share information to the vehicle, e.g.,tiered-data shared to vehicle 132, based on tiered-data sharing profileinformation 120 and vehicle information from vehicle 130. Informationshared with the vehicle, e.g., with a vehicle information sharingdevice, can enable the vehicle to share this information with internalor external service devices (not illustrated). As an example,tiered-data shared to vehicle 132 can enable a vehicle informationsharing device to share a toll pass QR code by generating an image ofthe QR code on a display that can be read by a toll booth device. Asanother example, tiered-data shared to vehicle 132 can enable a vehicleinformation sharing device to share a parking pass RF signal with aparking garage RF receiver. As a further example, tiered-data shared tovehicle 132 can enable a vehicle information sharing device to share atoken, subject to authorization via UI component 112, with an in-vehicleradio device to purchase a subscription to a satellite radio service. Itwill be noted that nearly any service can be interacted with by avehicle information sharing device to allow tiered-data sharing viamobile device 110 without departing from the scope of the subjectdisclosure and that not all examples are presented herein simply for thesake of clarity and brevity.

FIG. 2 is a depiction of a system 200 that can facilitate employing amobile device, receiving external tiered data, enabling tiered dataexchange for vehicle adaptation in accordance with aspects of thesubject disclosure. System 200 can include mobile device 210. Mobiledevice 210 can comprise UI component 212 and tiered-data accesscomponent 214. UI component 212 can receive an indication from a user ofmobile device 210. The indication can be related to sharing tiered datawith a vehicle, e.g., a vehicle information sharing device (notillustrated) of the vehicle. UI component 212 can be employed toimplement authorization or approval related to sharing tiered data witha vehicle. Further, UI component 212 can be employed to directly inputtiered data into mobile device 210. This can populate a tiered-datasharing profile. The profile can be stored on the device or external tothe device, e.g., on a server by uploading the tiered data input and/orprofile to the server. A tiered-data sharing profile can also be createdexternal to the mobile device and can be received by the device astiered-data sharing profile information 220.

A tiered-data sharing profile can comprise data to be shared, the dataassociated with a level or tier of sharing associated with securityrules, privacy rules, authorization rules, etc. Moreover, tiered-datasharing profile can comprise identifiers associated with data stored inan external store, e.g., account numbers or other account identifiers,account balances, tier rules, etc., such that a tiered data profile canbe employed to gather tiered-data from an external store. Tiered datacan be stored on an external store and can be received by mobile device210 as tiered-data from external data store 240. As an example, atiered-data sharing profile can identify a bridge toll pass accountresiding on a server operated by a bridge authority, such that,tiered-data sharing profile information 220, comprising informationrelated to the bridge toll pass account from the tiered-data sharingprofile, can facilitate a query of the bridge authority server toretrieve the account information, e.g., tiered-data from external datastore 240. In an embodiment, tiered-data sharing profile information 220can comprise tiered-data from external data store 240, e.g., tiered-datafrom external data store 240 can be employed to prepopulate atiered-data sharing profile with account information such thattiered-data sharing profile information 220 includes the accountinformation.

Vehicle information from vehicle 230 can be received by mobile device210. Vehicle information from vehicle 230 can be received via a wired orwireless link between the vehicle and mobile device 210. Vehicleinformation from vehicle 230 can comprise identification information,parameter information, subsystems information, vehicle informationsharing device information, etc. Vehicle information from vehicle 230can enable mobile device 210 to associate a vehicle with tiered-datasharing profile information 220. Vehicle information from vehicle 230can be used to request authentication of the vehicle from a userassociated with a tiered-data sharing profile, such as by presentinginformation about the vehicle to the user via UI component 212 andrequesting that the user approve associating the vehicle, e.g., vehicleinformation sharing device, with the tiered-data sharing profile of theuser.

Tiered-data access component 214 can determine access to tiered data.Access to tiered data can be based on tiered-data sharing profileinformation 220, vehicle information from vehicle 230, or tiered-datafrom external data store 240. Tiered-data access component 214 can applyrules stored on mobile device 210 or received in tiered-data sharingprofile information 220 to sharing tiered data. Further, tiered-dataaccess component 214 can share data based on information relating thevehicle information sharing device, such as, supported sharing formats(e.g., RF, images, audio, etc.), vehicle location (e.g., geofencing), orthe status of a vehicle association with a tiered-data sharing profile,etc. Moreover, tiered-data access component 214 can determine access totiered data based on the tiered data, such as, requesting or generatinga token for data in a tier associated with not directly sharing thedata, accessing an appropriate tiered-data format, etc.

In an aspect, tiered-data access component 214 can convert tiered databetween formats to allow tiered-data from external data store 240, ortiered data stored on mobile device 210, to be converted from a firstformat into a second format germane to a requesting internal or externalservice device. Conversion of data formats can also depend on thecapabilities of a vehicle information sharing device, whereininformation on these capabilities can be included in-vehicle informationfrom vehicle 230. As an example, where account data for a toll pass isrequested in QR format by a toll booth device, tiered-data accesscomponent 214 can convert a barcode version of the account data (e.g.,bar code version stored on mobile device 210) or can covert a numericalrepresentation (e.g., numerical representation of account data receivedin tiered-data from external data store 240) into a QR format forsharing with the vehicle information sharing device (e.g., tiered-datashared to vehicle 232 comprises QR version information). In an aspect,where the vehicle information from vehicle 230 comprises informationindicating that the vehicle information sharing device is unable todisplay a QR code, tiered-data access component 214 can negotiate analternative format with the toll booth device or can initiate a relevantmessage to the user via UI component 212.

Mobile device 210 can enable access to tiered-data shared to vehicle232. Mobile device 210 can share information to the vehicle, e.g.,tiered-data shared to vehicle 232, based on tiered-data sharing profileinformation 220, vehicle information from vehicle 230, and tiered-datafrom external data store 240. Information shared with the vehicle, e.g.,with a vehicle information sharing device, can enable the vehicle toshare this information with internal or external service devices (notillustrated). As an example, tiered-data shared to vehicle 232 canenable a vehicle information sharing device to share a toll pass barcode by generating an image of the bar code on a display that can beread by a toll booth device. It is to be noted that nearly any servicecan be interacted with by a vehicle information sharing device to allowtiered-data sharing via mobile device 210 without departing from thescope of the subject disclosure and that not all examples are presentedherein simply for the sake of clarity and brevity.

FIG. 3 illustrates a system 300 that facilitates employing a mobiledevice enabled tiered data exchange for vehicle adaptation and datatokens in accordance with aspects of the subject disclosure. System 300can include mobile device 310. Mobile device 310 can comprise UIcomponent 312 and tiered-data access component 314. UI component 312 canreceive an indication from a user of mobile device 310. The indicationcan be related to sharing tiered data with a vehicle, e.g., a vehicleinformation sharing device (not illustrated) of the vehicle. UIcomponent 312 can be employed to implement authorization or approvalrelated to sharing tiered data with a vehicle. Further, UI component 312can be employed to directly input tiered data into mobile device 310.This can populate a tiered-data sharing profile. The profile can bestored on the device or external to the device, e.g., on a server byuploading the tiered data input and/or profile to the server. Atiered-data sharing profile can also be created external to the mobiledevice and can be received by the device as tiered-data sharing profileinformation 320.

A tiered-data sharing profile can comprise data to be shared, the dataassociated with a level or tier of sharing associated with securityrules, privacy rules, authorization rules, etc. Moreover, tiered-datasharing profile can comprise identifiers associated with data stored inan external store, e.g., account numbers or other account identifiers,account balances, tier rules, etc., such that a tiered data profile canbe employed to gather tiered-data from an external store. Tiered datacan be stored on an external store, tiered-data store 362 of tiered-datacomponent 360, and can be received by mobile device 310 as part oftiered-data information 342. In an embodiment, tiered-data sharingprofile information 320 can comprise tiered-data from tiered-data store362, e.g., tiered-data from tiered-data store 362 can be employed toprepopulate a tiered-data sharing profile with account information suchthat tiered-data sharing profile information 320 includes the accountinformation.

Tiered-data information 342 can also comprise information relevant toreceiving stored tiered data from tiered-data component 360, e.g., fromtiered-data store 362. This can include requests for tiered datagenerated by mobile device 310 and communicated to tiered-data component360 as part of tiered-data information 342. Further, tiered-datainformation 342 can comprise information relevant to receivingrepresentations of stored tiered data that shield the tiered data, e.g.,a token. Token information can be stored on token information store 364of tiered-data component 360. Token information can include tokenidentifiers and corresponding tiered data, for example, a first tokencan be identified as ‘token 1234’ and can be associated with bank‘account number 987654321’ such that when ‘token 1234’ is redeemed by aninternal or external service, that service only has ‘token 1234’information but does not have ‘account number 987654321’ information.The redemption of ‘token 1234’ can be performed by a trusted partnerdevice (not illustrated) that can charge ‘account number 987654321’ andcredit the service correspondingly without exposing the bank accountnumber to the service. As such, tiered-data component 360, in anembodiment, can communicate with a trusted partner device to facilitateprocessing of tokens. This communication can be by way of mobile device310, such as, using a Wi-Fi connection of mobile device 310 tocommunicate token information from tiered-data component 360 to atrusted partner device.

Vehicle information from vehicle 330 can be received by mobile device310. Vehicle information from vehicle 330 can be received via a wired orwireless link between the vehicle and mobile device 310. Vehicleinformation from vehicle 330 can comprise identification information,parameter information, subsystems information, vehicle informationsharing device information, etc. Vehicle information from vehicle 330can enable mobile device 310 to associate a vehicle with tiered-datasharing profile information 320. Vehicle information from vehicle 330can be used to request authentication of the vehicle from a userassociated with a tiered-data sharing profile, such as by presentinginformation about the vehicle to the user via UI component 312 andrequesting that the user approve associating the vehicle, e.g., vehicleinformation sharing device, with the tiered-data sharing profile of theuser.

Tiered-data access component 314 can determine access to tiered data.Access to tiered data can be based on tiered-data sharing profileinformation 320, vehicle information from vehicle 330, or tiered-datainformation 342. Tiered-data access component 314 can apply rules storedon mobile device 310, or received in tiered-data sharing profileinformation 320, to sharing tiered data. Further, tiered-data accesscomponent 314 can share tiered data based on information relating thevehicle information sharing device, such as, supported sharing formats,vehicle location, or the status of a vehicle association with atiered-data sharing profile, etc. Moreover, tiered-data access component314 can determine access to tiered data based on the tiered data, suchas, requesting or generating a token for data in a tier associated withnot directly sharing the data, accessing an appropriate tiered-dataformat, etc. In an aspect, tiered-data access component 314 can converttiered data between formats to allow tiered-data from tiered-data store362, or tiered data stored on mobile device 310, to be converted from afirst format into a second format germane to a requesting internal orexternal service device.

Mobile device 310 can enable access to tiered-data shared to vehicle332. Mobile device 310 can share information to the vehicle, e.g.,tiered-data shared to vehicle 332, based on tiered-data sharing profileinformation 320, vehicle information from vehicle 330, and tiered-datainformation 342. Information shared with the vehicle, e.g., with avehicle information sharing device, can enable the vehicle to share thisinformation with internal or external service devices (not illustrated)via tiered data interface component 352. As an example, tiered-datashared to vehicle 332 can enable a vehicle information sharing device toshare a toll pass bar code by generating an image of the bar code on adisplay linked to tiered data interface component 352, such that, thebar code can be read by a toll booth device. Further, tiered datainterface component 352 can be linked to various vehicle subsystems tofacilitate communication of tiered-data shared to vehicle 332. As anexample, tiered data interface component 352 can be linked to a vehicleBLUETOOTH transponder to enable sharing of tiered-data shared to vehicle332 by BLUETOOTH with external service component 370. As anotherexample, tiered data interface component 352 can be linked to a vehiclebrake light system to enable sharing of tiered-data shared to vehicle332 by pulsing the brake lights. This can share vehicle operatorinformation with a police vehicle parked to the rear of the vehicle,e.g., the police vehicle can have an external service component 370 thatqueries the restrained vehicle and reads the pulsing brake lights toseek access to license and registration information associated with atiered-data sharing profile for a mobile device in the restrainedvehicle. It is to be noted that nearly any service can be interactedwith by a vehicle information sharing device to allow tiered-datasharing via mobile device 310 without departing from the scope of thesubject disclosure and that not all examples are presented herein simplyfor the sake of clarity and brevity.

FIG. 4 illustrates a system 400 that facilitates employing a mobiledevice enabled tiered data exchange for vehicle adaptation andcommunication of a data token from a token store device to an externalservice device in accordance with aspects of the subject disclosure.System 400 can include mobile device 410. Mobile device 410 can compriseUI component 412 and tiered-data access component 414. UI component 412can receive an indication from a user of mobile device 410. Theindication can be related to sharing tiered data with a vehicle, e.g., avehicle information sharing device (not illustrated) of the vehicle. UIcomponent 412 can be employed to implement authorization or approvalrelated to sharing tiered data with a vehicle. Further, UI component 412can be employed to directly input tiered data into mobile device 410.This can populate a tiered-data sharing profile. The profile can bestored on the device or external to the device, e.g., on a server byuploading the tiered data input and/or profile to the server. Atiered-data sharing profile can also be created external to the mobiledevice and can be received by the device as tiered-data sharing profileinformation 420.

A tiered-data sharing profile can comprise data to be shared, the dataassociated with a level or tier of sharing associated with securityrules, privacy rules, authorization rules, etc. Moreover, tiered-datasharing profile can comprise identifiers associated with data stored inan external store, e.g., account numbers or other account identifiers,account balances, tier rules, etc., such that a tiered data profile canbe employed to gather tiered-data from an external store. Tiered datacan be stored on an external store, tiered-data store 462 of tiered-datacomponent 460, and can be received by mobile device 410. In anembodiment, tiered-data sharing profile information 420 can comprisetiered-data from tiered-data store 462, e.g., tiered-data fromtiered-data store 462 can be employed to prepopulate a tiered-datasharing profile with account information such that tiered-data sharingprofile information 420 includes the account information.

Mobile device 410 can also receive information relevant to receivingrepresentations of stored tiered data that shield the tiered data, e.g.,a token. Token information can be stored on token information store 464of tiered-data component 460. Token information can include tokenidentifiers and corresponding tiered data. Tiered-data component 460, inan embodiment, can communicate with a trusted partner device tofacilitate processing of tokens. This communication can be by way ofmobile device 410.

Vehicle information from vehicle 430 can be received by mobile device410. Vehicle information from vehicle 430 can be received via a wired orwireless link between the vehicle and mobile device 410. Vehicleinformation from vehicle 430 can comprise identification information,parameter information, subsystems information, vehicle informationsharing device information, etc. Vehicle information from vehicle 430can enable mobile device 410 to associate a vehicle with tiered-datasharing profile information 420. Vehicle information from vehicle 430can be used to request authentication of the vehicle from a userassociated with a tiered-data sharing profile, such as by presentinginformation about the vehicle to the user via UI component 412 andrequesting that the user approve associating the vehicle, e.g., vehicleinformation sharing device, with the tiered-data sharing profile of theuser.

Tiered-data access component 414 can determine access to tiered data.Access to tiered data can be based on tiered-data sharing profileinformation 420, vehicle information from vehicle 430, or tiered-datainformation 442. Tiered-data access component 414 can apply rules storedon mobile device 410, or received in tiered-data sharing profileinformation 420, to sharing tiered data. Further, tiered-data accesscomponent 414 can share tiered data based on information relating thevehicle information sharing device, such as, supported sharing formats,vehicle location, or the status of a vehicle association with atiered-data sharing profile, etc. Moreover, tiered-data access component414 can determine access to tiered data based on the tiered data, suchas, requesting or generating a token for data in a tier associated withnot directly sharing the data, accessing an appropriate tiered-dataformat, etc. In an aspect, tiered-data access component 414 can converttiered data between formats to allow tiered-data from tiered-data store462, or tiered data stored on mobile device 410, to be converted from afirst format into a second format germane to a requesting internal orexternal service device.

Mobile device 410 can enable access to tiered-data shared to vehicle432. Mobile device 410 can share information to the vehicle, e.g.,tiered-data shared to vehicle 432, based on tiered-data sharing profileinformation 420, vehicle information from vehicle 430, and tiered-datainformation 442. Information shared with the vehicle, e.g., with avehicle information sharing device, can enable the vehicle to share thisinformation with internal or external service devices (not illustrated)via tiered data interface component 452. Further, tiered data interfacecomponent 452 can be linked to various vehicle subsystems to facilitatecommunication of tiered-data shared to vehicle 432. It is to be notedthat nearly any service can be interacted with by a vehicle informationsharing device to allow tiered-data sharing via mobile device 410without departing from the scope of the subject disclosure and that notall examples are presented herein simply for the sake of clarity andbrevity.

Further, tiered-data access component 414 can enable access totiered-data or tokens via tiered-data component 460. In some instances,such as where a vehicle information sharing device is incompatible withexternal service component 470, tiered data or tokens can be shared fromtiered-data component 460 with external service component 470 directly,bypassing the vehicle information sharing device. In other instances,such as where a mobile device runs out of power before it cancommunicate tiered-data to the vehicle, tiered-data component 460 cancommunicate the tiered data to the vehicle directly, where the vehiclehas communications capabilities.

Vehicle 450 can further comprise in-vehicle service component 480.In-vehicle service component 480 can allow for sharing tiered-data withservices associated with the vehicle itself. This can be very useful invehicles that are not owned by a user insomuch as vehicles owned byothers can often lack customizations that could be associated with auser owned vehicle. As an example, a user may have satellite radio intheir personal vehicle but satellite radio may be a premium option in ashared vehicle or a rental vehicle. In-vehicle service component 480 canallow tiered data, such as a user subscription to satellite radio, to becommunicated to the vehicle to allow that option to function in thevehicle. As an example, a user with a satellite radio subscription couldhave access both in their personal vehicle and in a rental vehicle inanother city simply by allowing the mobile device to share thesubscription account data with the rental vehicle. Similarly, where theuser does not have a satellite radio subscription, they can use a bankaccount linked to their tiered-data sharing profile to purchase asubscription in the vehicle by way of the in-vehicle service component480 in a manner as described elsewhere herein with regard to purchasingservices from an external service component 470.

FIG. 5 illustrates exemplary system 500 that employs a mobile deviceenabled tiered data exchange for vehicle adaptation and an external dataprovider in accordance with aspects of the subject disclosure. System500 can include mobile device 510. Mobile device 510 can comprise UIcomponent 512 and tiered-data access component 514. UI component 512 canreceive an indication from a user of mobile device 510. The indicationcan be related to sharing tiered data with a vehicle, e.g., a vehicleinformation sharing device (not illustrated) of the vehicle. UIcomponent 512 can be employed to implement authorization or approvalrelated to sharing tiered data with a vehicle. Further, UI component 512can be employed to directly input tiered data into mobile device 510.This can populate a tiered-data sharing profile. The profile can bestored on the device or external to the device, e.g., on a server byuploading the tiered data input and/or profile to the server. Atiered-data sharing profile can also be created external to the mobiledevice and can be received by the device as tiered-data sharing profileinformation 520.

A tiered-data sharing profile can comprise data to be shared, the dataassociated with a level or tier of sharing related to security rules,privacy rules, authorization rules, etc. Moreover, a tiered-data sharingprofile can comprise identifiers associated with data stored in anexternal store, e.g., account numbers or other account identifiers,account balances, tier rules, etc., such that a tiered data profile canbe employed to gather tiered-data from an external store. Tiered datacan be stored on an external store, tiered-data store 562 of tiered-datacomponent 560, and can be received by mobile device 510. In anembodiment, tiered-data sharing profile information 520 can comprisetiered-data from tiered-data store 562, e.g., tiered-data fromtiered-data store 562 can be employed to prepopulate a tiered-datasharing profile with account information such that tiered-data sharingprofile information 520 includes the account information.

Mobile device 510 can also receive information relevant to receivingrepresentations of stored tiered data that shield the tiered data, e.g.,a token. Token information can be stored on token information store 564of tiered-data component 560. Token information can include tokenidentifiers and corresponding tiered data. Tiered-data component 560, inan embodiment, can communicate with a trusted partner device tofacilitate processing of tokens. This communication can be by way ofmobile device 510.

Vehicle information from vehicle 530 can be received by mobile device510. Vehicle information from vehicle 530 can be received via a wired orwireless link between the vehicle and mobile device 510. Vehicleinformation from vehicle 530 can comprise identification information,parameter information, subsystems information, vehicle informationsharing device information, etc. Vehicle information from vehicle 530can enable mobile device 510 to associate a vehicle with tiered-datasharing profile information 520. Vehicle information from vehicle 530can be used to request authentication of the vehicle 550 from a userassociated with a tiered-data sharing profile, such as by presentinginformation about the vehicle to the user via UI component 512 andrequesting that the user approve associating the vehicle 550, e.g.,vehicle information sharing device, with the tiered-data sharing profileof the user.

Tiered-data access component 514 can determine access to tiered data.Access to tiered data can be based on tiered-data sharing profileinformation 520, vehicle information from vehicle 530, or tiered-datainformation 542. Tiered-data access component 514 can apply rules storedon mobile device 510, or received in tiered-data sharing profileinformation 520, to sharing tiered data. Further, tiered-data accesscomponent 514 can share tiered data based on information related to thevehicle information sharing device, such as, supported sharing formats,vehicle location, or the status of a vehicle association with atiered-data sharing profile, etc. Moreover, tiered-data access component514 can determine access to tiered data based on the tiered data, suchas, requesting or generating a token for data in a tier associated withnot directly sharing the data, accessing an appropriate tiered-dataformat, etc. In an aspect, tiered-data access component 514 can converttiered data between formats to allow tiered-data from tiered-data store562, or tiered data stored on mobile device 510, to be converted from afirst format into a second format germane to a requesting internal orexternal service device, e.g., external service component 570,in-vehicle service component 580, etc.

Mobile device 510 can enable access to tiered-data shared to vehicle532. Mobile device 510 can share information to the vehicle 550, e.g.,tiered-data shared to vehicle 532, based on tiered-data sharing profileinformation 520, vehicle information from vehicle 530, and tiered-datainformation 542. Information shared with vehicle 550, e.g., with avehicle information sharing device, can enable vehicle 550 to share thisinformation with internal or external service devices (not illustrated)via tiered data interface component 552. Further, tiered data interfacecomponent 552 can be linked to various vehicle subsystems to facilitatecommunication of tiered-data shared to vehicle 532. It is to be notedthat nearly any service can be interacted with by a vehicle informationsharing device to allow tiered-data sharing via mobile device 510without departing from the scope of the subject disclosure and that notall examples are presented herein simply for the sake of clarity andbrevity.

Further, tiered-data access component 514 can enable access totiered-data or tokens via tiered-data component 560. In some instances,tiered data or tokens can be shared from tiered-data component 560 withexternal service component 570 directly, bypassing the vehicleinformation sharing device. In other instances, tiered-data component560 can communicate the tiered data to the vehicle directly, where thevehicle has communications capabilities.

Vehicle 550 can further comprise in-vehicle service component 580.In-vehicle service component 580 can allow sharing of tiered-data withservices associated with the vehicle itself. In-vehicle servicecomponent 580 can allow tiered data to be communicated to vehicle 550 toallow adaptation of vehicle 550. As an example, a user with a trailheadpermit could have access to the trailhead permit in both their personalvehicle and a friend's vehicle by allowing the user's mobile device toshare the trailhead permit data with different vehicles. Also, where theuser does not have a trailhead permit, they can use a payment accountlinked to their tiered-data sharing profile to purchase the trailheadpermit for a vehicle by way of the in-vehicle service component 580 in amanner similar to that described elsewhere herein with regard topurchasing services from an external service component 570.

System 500 can further comprise external data provider component 590that can enable access to external data stored on external data store592 to facilitate adaptation of vehicle 550, such as by adapting avehicle information sharing device. External data provider component 590can be communicatively coupled to mobile device 510. In otherembodiments, external data provider component 590 can be communicativelycoupled to vehicle 550 or external service component 570. External dataprovider component 590 can source or provide access to data related totiered data or tiered-data information. In an aspect, this can includecontent related to an account, service, profile, etc. As an example, astreaming music service can source music content via external dataprovider component 590 based on tiered-data sharing profile information520 received by mobile device 510. In another example, tiered-dataaccess component 514 can enable access to a token to purchase a carwash, and external data provider component 590 can provide supplementaryinformation related to the type of car wash to be provided, such asdesignating wash only, wash and wax only, wash and wax and undercarriagecleaning only, etc. As a further example, where mobile device 510provides vehicle 550 with a token for a ‘quicklube’ type vehicleservice, external data provider component 590 can provide informationrelated to the type and weight of the motor oil to be used on thevehicle, a preferred brand of air filter, etc. External data can beassociated with tiered-data sharing profile information 520 or withvehicle information from vehicle 530. This can enable, for example, auser to take a shared vehicle in for services subject to vehicle ownerparameters provided via external data from external data providercomponent 590, e.g., the user can pay for a vehicle service visit whilethe external data helps ensure that parts approved by the vehicle ownerare used in the service. As an example, a shared vehicle operated byZippyShareCarCompany can be used by Fred. ZippyShareCarCompany canpopulate an external data store, e.g., 592, with repair information,such as acceptable replacement tires. When Fred takes the vehicle in toreplace a blown out tire, Fred's smartphone can provide a token to payfor the new tire and receive external data from external data providercomponent 590 indicating what replacement tires are acceptable toZippyShareCarCompany. As such, an acceptable replacement tire can beselected by a repair shop via external service component 570.

In an embodiment, external data provider component 590 can directlysource external data to vehicle 550 or external service component 570.Mobile device 510 can provide information to external data component 590to enable external data provider component 590 to source external datato vehicle 550 or external service component 570. As an example, whereFred is replacing a blown out tire on a car borrowed fromZippyShareCarCompany, mobile device 510 can provide external dataprovider component 590 with ZippyShareCarCompany information, allowingexternal data provider component 590 to send acceptable tire informationdirectly to ZippyShareCarCompany rather than passing the tireinformation through Fred's mobile device. As another example, streamingmusic data can be directed to vehicle 550, rather than being passedthrough mobile device 510, based on information received by externaldata provider component 590 from mobile device 510 in relation totiered-data sharing profile information 520.

In view of the example system(s) described above, example method(s) thatcan be implemented in accordance with the disclosed subject matter canbe better appreciated with reference to flowcharts in FIG. 6-FIG. 8. Forpurposes of simplicity of explanation, example methods disclosed hereinare presented and described as a series of acts; however, it is to beunderstood and appreciated that the claimed subject matter is notlimited by the order of acts, as some acts may occur in different ordersand/or concurrently with other acts from that shown and describedherein. For example, one or more example methods disclosed herein couldalternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, interaction diagram(s) mayrepresent methods in accordance with the disclosed subject matter whendisparate entities enact disparate portions of the methods. Furthermore,not all illustrated acts may be required to implement a describedexample method in accordance with the subject specification. Furtheryet, two or more of the disclosed example methods can be implemented incombination with each other, to accomplish one or more aspects hereindescribed. It should be further appreciated that the example methodsdisclosed throughout the subject specification are capable of beingstored on an article of manufacture (e.g., a computer-readable medium)to allow transporting and transferring such methods to computers forexecution, and thus implementation, by a processor or for storage in amemory.

FIG. 6 illustrates aspects of method 600 facilitating employing a mobiledevice enabled tiered data exchange for vehicle adaptation in accordancewith aspects of the subject disclosure. At 610, method 600 can includereceiving vehicle information by a mobile device. A mobile device can bea smartphone, tablet computer, laptop computer, or any other type ofmobile device. Vehicle information can be received by the mobile devicethrough a wired or wireless link. Vehicle information can compriseidentification information, parameter information, subsystemsinformation, vehicle information sharing device information, etc.Vehicle information can enable the mobile device to associate thevehicle with tiered-data sharing profile information. A tiered-datasharing profile can comprise data to be shared, wherein the data can beassociated with a level or tier of sharing associated with securityrules, privacy rules, authorization rules, etc. In an embodiment,vehicle information can be from a vehicle in close proximity to themobile device, e.g., where the mobile device is within the vehicle.Vehicle information can be used to request authentication of the vehiclefrom a user associated with a tiered-data sharing profile, such as bypresenting information about the vehicle to a user via a user interfacecomponent and requesting that the user approve associating the vehiclewith tiered-data sharing profile information, e.g., associating avehicle information sharing device with a tiered-data sharing profile ofthe user.

In an embodiment, an association of a vehicle with tiered-data sharingprofile information can persist such that a user does not need toapprove a vehicle each time they are near it. In another embodiment, theassociation can be non-persistent, such that the user is always asked toauthorize a vehicle. Further embodiments can include associationpersistence rules. These rules can, for example, persist some vehicleassociations and not others, can persist a vehicle association for adetermined time, persist a vehicle association so long as a determinednumber of new associations have not been created, etc.

At 620, method 600 can include the mobile device receiving tiered-datasharing profile information. Tiers of tiered data can be associated withcorresponding levels of security, privacy, and authorizations,locations, areas, times, rules, etc. Tiered-data sharing profileinformation can be information relating to a tiered-data sharingprofile. A tiered-data sharing profile can be located on the mobiledevice or can be located external to the mobile device, e.g., on aserver or external storage device. In an embodiment, a user interface ofthe mobile device can be used to create, delete, or modify a tiered-datasharing profile. In another embodiment, a tiered-data sharing profilecan be created, deleted, or modified on a device other than the mobiledevice, e.g., on a personal computer, tablet computer, server, etc. Asan example of different data tiers, a first tier can be associated withsharing of the data itself based on association of the tiered-datasharing profile with a vehicle, a second tier can be associated withsharing of the data itself based on association of the tiered-datasharing profile with a vehicle and a further authorization by theassociated user, and a third tier can be associated with sharing of arepresentation of the data without sharing the data itself, e.g., atoken of the data, association of the tiered-data sharing profile with avehicle and a further authorization by the associated user. It will benoted that any number of tiers can be employed without departing fromthe scope of the disclosed subject matter. Similarly, it will be notedthat nearly any combination of security features, privacy features,authorization techniques, etc., can be employed in enabling access todata associated with a tier without departing from the scope of theinstant application.

At 630, method 600 can comprise the mobile device enabling access totiered-data based on the tiered-data sharing profile. At this point,method 600 can end. Information shared with the vehicle, such as,enabling access to tiered data by a vehicle information sharing deviceof a vehicle, can enable the vehicle to further share this informationwith internal or external service devices. As an example, tiered-datashared to the vehicle can enable a vehicle information sharing device toshare a toll pass code by generating an image of the code on a displaythat can be read by a toll booth device. As another example, tiered-datashared to the vehicle can enable a vehicle information sharing device toshare a parking pass infrared signal with a parking garage infraredreceiver. As a further example, tiered-data shared to the vehicle canenable a vehicle information sharing device to share a token, subject toauthorization via a user interface component of the mobile device orvehicle, to purchase a subscription to a satellite radio service.

It will be noted that nearly any service can be interacted with by avehicle information sharing device to allow tiered-data sharing via themobile device without departing from the scope of the subject disclosureand that not all examples are presented herein simply for the sake ofclarity and brevity. Moreover, nearly any vehicle subsystem can besubject to adaptation or control based on information related to sharedtiered data. As an example, headlights can be adapted to flash codes, astereo system can be adapted to play an audio code, a vehicle BLUETOOTHtransceiver can be adapted to transmit a signal, etc. Further, as statedherein, a vehicle information sharing device can share information withan internal or external service by way of RF, images, modulated light,audio tones, etc. With this in mind, it will be noted that a vehicle canemploy more than one subsystem to share information, e.g., flashingheadlights, audio tones on the stereo, and RF codes from a BLUETOOTHadapter, to share information with one or more internal or externalservices based on information related to a tiered-data sharing profile.

FIG. 7 illustrates a method 700 that facilitates employing a mobiledevice enabled tiered data exchange for vehicle adaptation comprisingauthorization via the mobile device in accordance with aspects of thesubject disclosure. At 710, method 700 can include receiving vehicleinformation by a mobile device. A mobile device can be a smartphone,tablet computer, laptop computer, or any other type of mobile device.Vehicle information can be received by the mobile device through a wiredor wireless link. Vehicle information can comprise identificationinformation, parameter information, subsystems information, vehicleinformation sharing device information, etc. Vehicle information canenable the mobile device to associate the vehicle with tiered-datasharing profile information. A tiered-data sharing profile can comprisedata to be shared, wherein the data can be associated with a level ortier of sharing associated with security rules, privacy rules,authorization rules, etc. In an embodiment, vehicle information can befrom a vehicle in close proximity to the mobile device, e.g., where themobile device is within the vehicle. Vehicle information can be used torequest authentication of the vehicle from a user associated with atiered-data sharing profile, such as by presenting information about thevehicle to a user via a user interface component and requesting that theuser approve associating the vehicle with tiered-data sharing profileinformation, e.g., associating a vehicle information sharing device witha tiered-data sharing profile of the user.

In an embodiment, an association of a vehicle with tiered-data sharingprofile information can persist such that a user does not need toapprove a vehicle each time they are near it. In another embodiment, theassociation can be non-persistent, such that the user is regularly askedto authorize a vehicle. Further embodiments can include associationpersistence rules. These rules, for example, can persist some vehicleassociations and not others, can persist a vehicle association for adetermined time, persist a vehicle association so long as a determinednumber of new associations have not been created, etc.

At 720, method 700 can include the mobile device receiving tiered-datasharing profile information. Tiers of tiered data can be associated withcorresponding levels of security, privacy, and authorizations,locations, areas, times, rules, etc. Tiered-data sharing profileinformation can be information relating to a tiered-data sharingprofile. A tiered-data sharing profile can be located on the mobiledevice or can be located external to the mobile device, e.g., on aserver or external storage device. In an embodiment, a user interface ofthe mobile device can be used to create, delete, or modify a tiered-datasharing profile. In another embodiment, a tiered-data sharing profilecan be created, deleted, or modified on a device other than the mobiledevice, e.g., on a personal computer, tablet computer, server, etc. Asan example of different data tiers, a first tier can be associated withsharing of the data itself based on association of the tiered-datasharing profile with a vehicle, a second tier can be associated withsharing of the data itself based on association of the tiered-datasharing profile with a vehicle and a further authorization by theassociated user, and a third tier can be associated with sharing of arepresentation of the data without sharing the data itself, e.g., atoken of the data, association of the tiered-data sharing profile with avehicle and a further authorization by the associated user. It will benoted that any number of tiers can be employed without departing fromthe scope of the disclosed subject matter. Similarly, it will be notedthat nearly any combination of security features, privacy features,authorization techniques, etc., can be employed in enabling access todata associated with a tier without departing from the scope of theinstant application.

At 730, method 700 can comprise the mobile device receiving a request toshare data including tiered data. In response to receiving the request,the mobile device can initiate sharing tiered-data subject to theconstraints of the associated tier parameters, such as, security rules,privacy rules, authorization rules, etc. The sharing can also be subjectto vehicle information sharing device parameters, such as, the types ofcommunication supported by the vehicle, etc. In an embodiment, therequest to share data can be received via a vehicle associated with atiered-data sharing profile of the mobile device, such as, a toll boothdevice can request payment from a vehicle information sharing devicewhich, in turn, can request that toll pass data or payment data beshared from the mobile device based on the tiered-data sharing profileinformation. In another embodiment, the request to share data can bereceived by the mobile device from an external service component. As anexample, a toll booth device can request payment or toll pass data fromthe mobile device based on a tiered-data sharing profile information,which can the mobile device to effect sharing the toll pass data orpayment data with the toll booth device via the vehicle, e.g., by way ofa vehicle sharing information device of the vehicle.

At 740, method 700 can include the mobile device receiving sharingauthorization to share tiered data. The mobile device can be employed toimplement authorization or approval related to sharing tiered data witha vehicle information sharing device. As an example, a mobile deviceuser interface component can receive a password, fingerprint, voiceprint, iris scan, etc. as part of authorizing sharing of tiered-datawith the vehicle. In an embodiment, the mobile device can receiveauthorization from an external source, such as a user enteringauthorization into a vehicle based user interface, such that theauthorization is then sent to the mobile device.

At 750, method 700 can comprise the mobile device enabling access totiered-data based on the tiered-data sharing profile. At this point,method 700 can end. Information shared with the vehicle, such as,enabling access to tiered data by a vehicle information sharing deviceof a vehicle, can enable the vehicle to further share this informationwith internal or external service devices. As an example, tiered-datashared to the vehicle can enable a vehicle information sharing device toshare a toll pass code by generating an image of the code on a displaythat can be read by a toll booth device. As another example, tiered-datashared to the vehicle can enable a vehicle information sharing device toshare a parking pass infrared signal with a parking garage infraredreceiver. As a further example, tiered-data shared to the vehicle canenable a vehicle information sharing device to share a token, subject toauthorization via a user interface component of the mobile device orvehicle, to purchase a subscription to a satellite radio service.

It will be noted that nearly any service can be interacted with by avehicle information sharing device to allow tiered-data sharing via themobile device without departing from the scope of the subject disclosureand that not all examples are presented herein simply for the sake ofclarity and brevity. Moreover, nearly any vehicle subsystem can besubject to adaptation or control based on information related to sharedtiered data. As an example, headlights can be adapted to flash codes, astereo system can be adapted to play an audio code, a vehicle BLUETOOTHtransceiver can be adapted to transmit a signal, etc. Further, as statedherein, a vehicle information sharing device can share information withan internal or external service by way of RF, images, modulated light,audio tones, etc. With this in mind, it will be noted that a vehicle canemploy more than one subsystem to share information, e.g., flashingheadlights, audio tones on the stereo, and RF codes from a BLUETOOTHadapter, to share information with one or more internal or externalservices based on information related to a tiered-data sharing profile.

FIG. 8 illustrates a method 800 that facilitates employing a mobiledevice enabled tiered data exchange for vehicle adaptation and datatokens in accordance with aspects of the subject disclosure. At 810,method 800 can include receiving vehicle information. Vehicleinformation can be received through a wired or wireless link. Vehicleinformation can comprise identification information, parameterinformation, subsystems information, vehicle information sharing deviceinformation, etc. Vehicle information can enable associating the vehiclewith tiered-data sharing profile information. A tiered-data sharingprofile can comprise data to be shared, wherein the data can beassociated with a level or tier of sharing associated with securityrules, privacy rules, authorization rules, etc. In an embodiment,vehicle information can be from a vehicle in close proximity to a mobiledevice, e.g., where the mobile device is within the vehicle. Vehicleinformation can be used to request authentication of the vehicle from amobile device associated with a tiered-data sharing profile, such as bypresenting information about the vehicle to a user via a user interfaceof the mobile device and requesting that the user approve associatingthe vehicle with tiered-data sharing profile information, e.g.,associating a vehicle information sharing device with a tiered-datasharing profile of the user. In an embodiment, an association of avehicle with tiered-data sharing profile information can persist suchthat a user does not need to approve a vehicle each time they are nearit. In another embodiment, the association can be non-persistent, suchthat the user is regularly asked to authorize a vehicle. Furtherembodiments can include association persistence rules.

At 820, method 800 can include receiving tiered-data sharing profileinformation. Tiers for data can be associated with corresponding levelsof security, privacy, authorizations, locations, areas, times, rules,etc. Tiered-data sharing profile information can be information relatingto a tiered-data sharing profile. A tiered-data sharing profile can belocated on a mobile device or can be located external to a mobiledevice, e.g., on a server or storage device. In an embodiment, a userinterface of a mobile device can be used to create, delete, or modify atiered-data sharing profile. In another embodiment, a tiered-datasharing profile can be created, deleted, or modified on a device otherthan a mobile device, e.g., on a personal computer, tablet computer,server, computer workstation, etc. As an example of different datatiers, a first tier can be associated with sharing of the data itselfbased on association of the tiered-data sharing profile with a vehicle,a second tier can be associated with sharing of the data itself based onassociation of the tiered-data sharing profile with a vehicle and afurther authorization by the associated user, and a third tier can beassociated with sharing of a representation of the data without sharingthe data itself, e.g., a token of the data, association of thetiered-data sharing profile with a vehicle and a further authorizationby the associated user. It will be noted that any number of tiers can beemployed without departing from the scope of the disclosed subjectmatter. Similarly, it will be noted that nearly any combination ofsecurity features, privacy features, authorization techniques, etc., canbe employed in enabling access to data associated with a tier withoutdeparting from the scope of the instant application.

At 830, method 800 can comprise receiving a request to share dataincluding tiered data. In response to receiving the request, sharingtiered-data can be initiated subject to constraints of the associatedtier parameters, such as, security rules, privacy rules, authorizationrules, etc. The sharing can also be subject to vehicle informationsharing device parameters, such as, the types of communication supportedby the vehicle, etc. In an embodiment, the request to share data can bereceived via a vehicle associated with a tiered-data sharing profile. Inanother embodiment, the request to share data can be received from anexternal service component.

At 840, method 800 can include the generating a token associated withtiered data to obfuscate tiered data. High sensitivity data can beassociated with a data tier employing digital tokens, hereinafter atoken, as a form a securing the data itself. As an example, sharing atoken of data, rather than the data itself, does not expose the dataitself but does allow exchange of the token for reconciliation of atransaction. As such, a vehicle battery charging station, for example,can request a payment in exchange for charging an electric vehiclebattery by transmitting a signal to the vehicle. The vehicle can beaffiliated with a tiered-data sharing profile indicating payments ofthis type are in a tier that employs a token rather than exposing actualdata, such as, a bank account number, a credit card number, etc. Thevehicle can share a token with the battery charging service. The tokencan be redeemed by a reconciling system of the battery charging serviceresulting in funds being paid to the charging service and,correspondingly, funds being withdrawn from the bank account or creditcard identified in the tiered-data sharing profile. This occurs, thoughuse of a token, without sharing the bank account number or credit cardnumber with the charging service. Tokens can be exchanged, for example,via a reconciliation service provider, with the mobile service provider,with a bank, etc. The tokens can also be associated with rules, such asexpiration conditions, time limits, value limits, secondaryauthorization, etc.

At 850, method 800 can include receiving sharing authorization to sharetiered data and the token. A mobile device can be employed to implementauthorization or approval related to sharing tiered data and tokens. Asan example, a mobile device user interface component can receive apassword, fingerprint, voice print, iris scan, etc. as part ofauthorizing sharing of tiered-data and tokens. In an embodiment,authorization can be received from an external source, such as a userentering authorization into a vehicle based user interface, a userinterface of an external service device, etc.

At 860, method 800 can comprise enabling access to tiered-data and tokenbased on the tiered-data sharing profile. At this point, method 800 canend. Information shared with the vehicle, such as, enabling access totiered data and tokens by a vehicle information sharing device of avehicle, can enable the vehicle to further share this information withinternal or external service devices. As an example, tiered-data sharedto the vehicle can enable a vehicle information sharing device to sharea token to pay a bridge toll by generating an image representing thetoken information on a display that can be read by a toll booth device.In an aspect, the token can be represented by a QR code, a bar code, asymbolic code, modulated light, modulated sound pressure, etc. Asanother example, a token shared to a vehicle can enable a vehicleinformation sharing device to share the token with a parking garageinfrared receiver. As a further example, a token shared to a vehicle canenable a vehicle information sharing device to share the token to effectpurchase a subscription to a satellite radio service within the vehicle.

It will be noted that nearly any service can be interacted with by avehicle information sharing device to allow tiered-data sharing via themobile device without departing from the scope of the subject disclosureand that not all examples are presented herein simply for the sake ofclarity and brevity. Moreover, nearly any vehicle subsystem can besubject to adaptation or control based on information related to sharedtiered data. As an example, headlights can be adapted to flash codes, astereo system can be adapted to play an audio code, a vehicle BLUETOOTHtransceiver can be adapted to transmit a signal, etc. Further, as statedherein, a vehicle information sharing device can share information withan internal or external service by way of RF, images, modulated light,audio tones, etc. With this in mind, it will be noted that a vehicle canemploy more than one subsystem to share information, e.g., flashingheadlights, audio tones on the stereo, and RF codes from a BLUETOOTHadapter, to share information with one or more internal or externalservices based on information related to a tiered-data sharing profile.

FIG. 9 is a schematic block diagram of a computing environment 900 withwhich the disclosed subject matter can interact. The system 900 includesone or more remote component(s) 910. The remote component(s) 910 can behardware and/or software (e.g., threads, processes, computing devices).In some embodiments, remote component(s) 910 can include servers,personal servers, wireless telecommunication network devices, etc. As anexample, remote component(s) 910 can be a device of a wireless carriernetwork, e.g., a RAN. As another example, remote component(s) 910 can bea server associated with a cloud computing provider device.

The system 900 also includes one or more local component(s) 920. Thelocal component(s) 920 can be hardware and/or software (e.g., threads,processes, computing devices). In some embodiments, local component(s)920 can include mobile device 110, 210, 310, 410, 510, etc. As anexample, local component(s) 920 can be a smartphone configured toreceive tiered-data sharing profile information, e.g., 120, etc.

One possible communication between a remote component(s) 910 and a localcomponent(s) 920 can be in the form of a data packet adapted to betransmitted between two or more computer processes. Another possiblecommunication between a remote component(s) 910 and a local component(s)920 can be in the form of circuit-switched data adapted to betransmitted between two or more computer processes in radio time slots.As an example, tiered-data sharing profile information, tiered-data,vehicle information, etc., can be communicated over a packet-switched orcircuit-switched channels between remote component 910, and a mobiledevice, e.g., a local component 920, via an air interface, such as on apacket-switched or circuit-switched downlink channel. The system 900includes a communication framework 940 that can be employed tofacilitate communications between the remote component(s) 910 and thelocal component(s) 920, and can include an air interface, e.g., Uuinterface of a UMTS network. Remote component(s) 910 can be operablyconnected to one or more remote data store(s) 950, such as a tiered-datastore 562, data token information store 564, external data store 592,etc., that can be employed to store information, such as tiered data, atiered-data sharing profile, etc., on the remote component(s) 910 sideof communication framework 940. Similarly, local component(s) 920 can beoperably connected to one or more local data store(s) 930, that can beemployed to store information, such as received tiered data, receivedtiered-data sharing profile information, etc., on the to the localcomponent(s) 920 side of communication framework 940.

In order to provide a context for the various aspects of the disclosedsubject matter, FIG. 10, and the following discussion, are intended toprovide a brief, general description of a suitable environment in whichthe various aspects of the disclosed subject matter can be implemented.While the subject matter has been described above in the general contextof computer-executable instructions of a computer program that runs on acomputer and/or computers, those skilled in the art will recognize thatthe disclosed subject matter also can be implemented in combination withother program modules. Generally, program modules include routines,programs, components, data structures, etc. that performs particulartasks and/or implement particular abstract data types.

In the subject specification, terms such as “store,” “storage,” “datastore,” data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It is noted that thememory components described herein can be either volatile memory ornonvolatile memory, or can include both volatile and nonvolatile memory,by way of illustration, and not limitation, volatile memory 1020 (seebelow), non-volatile memory 1022 (see below), disk storage 1024 (seebelow), and memory storage 1046 (see below). Further, nonvolatile memorycan be included in read only memory, programmable read only memory,electrically programmable read only memory, electrically erasable readonly memory, or flash memory. Volatile memory can include random accessmemory, which acts as external cache memory. By way of illustration andnot limitation, random access memory is available in many forms such assynchronous random access memory, dynamic random access memory,synchronous dynamic random access memory, double data rate synchronousdynamic random access memory, enhanced synchronous dynamic random accessmemory, Synchlink dynamic random access memory, and direct Rambus randomaccess memory. Additionally, the disclosed memory components of systemsor methods herein are intended to comprise, without being limited tocomprising, these and any other suitable types of memory.

Moreover, it is noted that the disclosed subject matter can be practicedwith other computer system configurations, including single-processor ormultiprocessor computer systems, mini-computing devices, mainframecomputers, as well as personal computers, hand-held computing devices(e.g., personal digital assistant, phone, watch, tablet computers,netbook computers, . . . ), microprocessor-based or programmableconsumer or industrial electronics, and the like. The illustratedaspects can also be practiced in distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network; however, some if not all aspects ofthe subject disclosure can be practiced on stand-alone computers. In adistributed computing environment, program modules can be located inboth local and remote memory storage devices.

FIG. 10 illustrates a block diagram of a computing system 1000 operableto execute the disclosed systems and methods in accordance with anembodiment. Computer 1012, which can be, for example, part of mobiledevice 110, 210, 310, 410, 510, etc., tiered-data component 360, 460,560, etc., or employing method 600, 700, or 800, etc., includes aprocessing unit 1014, a system memory 1016, and a system bus 1018.System bus 1018 couples system components including, but not limited to,system memory 1016 to processing unit 1014. Processing unit 1014 can beany of various available processors. Dual microprocessors and othermultiprocessor architectures also can be employed as processing unit1014.

System bus 1018 can be any of several types of bus structure(s)including a memory bus or a memory controller, a peripheral bus or anexternal bus, and/or a local bus using any variety of available busarchitectures including, but not limited to, industrial standardarchitecture, micro-channel architecture, extended industrial standardarchitecture, intelligent drive electronics, video electronics standardsassociation local bus, peripheral component interconnect, card bus,universal serial bus, advanced graphics port, personal computer memorycard international association bus, Firewire (Institute of Electricaland Electronics Engineers 1194), and small computer systems interface.

System memory 1016 can include volatile memory 1020 and nonvolatilememory 1022. A basic input/output system, containing routines totransfer information between elements within computer 1012, such asduring start-up, can be stored in nonvolatile memory 1022. By way ofillustration, and not limitation, nonvolatile memory 1022 can includeread only memory, programmable read only memory, electricallyprogrammable read only memory, electrically erasable read only memory,or flash memory. Volatile memory 1020 includes read only memory, whichacts as external cache memory. By way of illustration and notlimitation, read only memory is available in many forms such assynchronous random access memory, dynamic read only memory, synchronousdynamic read only memory, double data rate synchronous dynamic read onlymemory, enhanced synchronous dynamic read only memory, Synchlink dynamicread only memory, Rambus direct read only memory, direct Rambus dynamicread only memory, and Rambus dynamic read only memory.

Computer 1012 can also include removable/non-removable,volatile/non-volatile computer storage media. FIG. 10 illustrates, forexample, disk storage 1024. Disk storage 1024 includes, but is notlimited to, devices like a magnetic disk drive, floppy disk drive, tapedrive, flash memory card, or memory stick. In addition, disk storage1024 can include storage media separately or in combination with otherstorage media including, but not limited to, an optical disk drive suchas a compact disk read only memory device, compact disk recordabledrive, compact disk rewritable drive or a digital versatile disk readonly memory. To facilitate connection of the disk storage devices 1024to system bus 1018, a removable or non-removable interface is typicallyused, such as interface 1026.

Computing devices typically include a variety of media, which caninclude computer-readable storage media or communications media, whichtwo terms are used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media can include,but are not limited to, read only memory, programmable read only memory,electrically programmable read only memory, electrically erasable readonly memory, flash memory or other memory technology, compact disk readonly memory, digital versatile disk or other optical disk storage,magnetic cassettes, magnetic tape, magnetic disk storage or othermagnetic storage devices, or other tangible media which can be used tostore desired information. In this regard, the term “tangible” herein asmay be applied to storage, memory or computer-readable media, is to beunderstood to exclude only propagating intangible signals per se as amodifier and does not relinquish coverage of all standard storage,memory or computer-readable media that are not only propagatingintangible signals per se. In an aspect, tangible media can includenon-transitory media wherein the term “non-transitory” herein as may beapplied to storage, memory or computer-readable media, is to beunderstood to exclude only propagating transitory signals per se as amodifier and does not relinquish coverage of all standard storage,memory or computer-readable media that are not only propagatingtransitory signals per se. Computer-readable storage media can beaccessed by one or more local or remote computing devices, e.g., viaaccess requests, queries or other data retrieval protocols, for avariety of operations with respect to the information stored by themedium.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and includes any information deliveryor transport media. The term “modulated data signal” or signals refersto a signal that has one or more of its characteristics set or changedin such a manner as to encode information in one or more signals. By wayof example, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

It can be noted that FIG. 10 describes software that acts as anintermediary between users and computer resources described in suitableoperating environment 1000. Such software includes an operating system1028. Operating system 1028, which can be stored on disk storage 1024,acts to control and allocate resources of computer system 1012. Systemapplications 1030 take advantage of the management of resources byoperating system 1028 through program modules 1032 and program data 1034stored either in system memory 1016 or on disk storage 1024. It is to benoted that the disclosed subject matter can be implemented with variousoperating systems or combinations of operating systems.

A user can enter commands or information into computer 1012 throughinput device(s) 1036. As an example, a user interface, such as UIcomponent 112, 212, 312, 412, 512, etc., can be embodied in a touchsensitive display panel allowing a user to interact with computer 1012.Input devices 1036 include, but are not limited to, a pointing devicesuch as a mouse, trackball, stylus, touch pad, keyboard, microphone,joystick, game pad, satellite dish, scanner, TV tuner card, digitalcamera, digital video camera, web camera, cell phone, smartphone, tabletcomputer, etc. These and other input devices connect to processing unit1014 through system bus 1018 by way of interface port(s) 1038. Interfaceport(s) 1038 include, for example, a serial port, a parallel port, agame port, a universal serial bus, an infrared port, a Bluetooth port,an IP port, or a logical port associated with a wireless service, etc.Output device(s) 1040 use some of the same type of ports as inputdevice(s) 1036.

Thus, for example, a universal serial busport can be used to provideinput to computer 1012 and to output information from computer 1012 toan output device 1040. Output adapter 1042 is provided to illustratethat there are some output devices 1040 like monitors, speakers, andprinters, among other output devices 1040, which use special adapters.Output adapters 1042 include, by way of illustration and not limitation,video and sound cards that provide means of connection between outputdevice 1040 and system bus 1018. It should be noted that other devicesand/or systems of devices provide both input and output capabilitiessuch as remote computer(s) 1044. As an example, vehicle subsystems, suchas headlights, brake lights, stereos, vehicle information sharingdevice, etc., can include an output adapter 1042 to enable use inaccordance with the presently disclosed subject matter.

Computer 1012 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)1044. Remote computer(s) 1044 can be a personal computer, a server, arouter, a network PC, cloud storage, cloud service, a workstation, amicroprocessor based appliance, a peer device, or other common networknode and the like, and typically includes many or all of the elementsdescribed relative to computer 1012.

For purposes of brevity, only a memory storage device 1046 isillustrated with remote computer(s) 1044. Remote computer(s) 1044 islogically connected to computer 1012 through a network interface 1048and then physically connected by way of communication connection 1050.Network interface 1048 encompasses wire and/or wireless communicationnetworks such as local area networks and wide area networks. Local areanetwork technologies include fiber distributed data interface, copperdistributed data interface, Ethernet, Token Ring and the like. Wide areanetwork technologies include, but are not limited to, point-to-pointlinks, circuit-switching networks like integrated services digitalnetworks and variations thereon, packet switching networks, and digitalsubscriber lines. As noted below, wireless technologies may be used inaddition to or in place of the foregoing.

Communication connection(s) 1050 refer(s) to hardware/software employedto connect network interface 1048 to bus 1018. While communicationconnection 1050 is shown for illustrative clarity inside computer 1012,it can also be external to computer 1012. The hardware/software forconnection to network interface 1048 can include, for example, internaland external technologies such as modems, including regular telephonegrade modems, cable modems and digital subscriber line modems,integrated services digital network adapters, and Ethernet cards.

The above description of illustrated embodiments of the subjectdisclosure, including what is described in the Abstract, is not intendedto be exhaustive or to limit the disclosed embodiments to the preciseforms disclosed. While specific embodiments and examples are describedherein for illustrative purposes, various modifications are possiblethat are considered within the scope of such embodiments and examples,as those skilled in the relevant art can recognize.

In this regard, while the disclosed subject matter has been described inconnection with various embodiments and corresponding Figures, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit, a digital signalprocessor, a field programmable gate array, a programmable logiccontroller, a complex programmable logic device, a discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. Processorscan exploit nano-scale architectures such as, but not limited to,molecular and quantum-dot based transistors, switches and gates, inorder to optimize space usage or enhance performance of user equipment.A processor may also be implemented as a combination of computingprocessing units.

As used in this application, the terms “component,” “system,”“platform,” “layer,” “selector,” “interface,” and the like are intendedto refer to a computer-related entity or an entity related to anoperational apparatus with one or more specific functionalities, whereinthe entity can be either hardware, a combination of hardware andsoftware, software, or software in execution. As an example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration and not limitation, both anapplication running on a server and the server can be a component. Oneor more components may reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media having various datastructures stored thereon. The components may communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal). Asanother example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, which is operated by a software or firmwareapplication executed by a processor, wherein the processor can beinternal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can include a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

Further, the term “include” is intended to be employed as an open orinclusive term, rather than a closed or exclusive term. The term“include” can be substituted with the term “comprising” and is to betreated with similar scope, unless otherwise explicitly used otherwise.As an example, “a basket of fruit including an apple” is to be treatedwith the same breadth of scope as, “a basket of fruit comprising anapple.”

Moreover, terms like “user equipment (UE),” “mobile station,” “mobile,”subscriber station,” “subscriber equipment,” “access terminal,”“terminal,” “handset,” and similar terminology, refer to a wirelessdevice utilized by a subscriber or user of a wireless communicationservice to receive or convey data, control, voice, video, sound, gaming,or substantially any data-stream or signaling-stream. The foregoingterms are utilized interchangeably in the subject specification andrelated drawings. Likewise, the terms “access point,” “base station,”“Node B,” “evolved Node B,” “home Node B,” “home access point,” and thelike, are utilized interchangeably in the subject application, and referto a wireless network component or appliance that serves and receivesdata, control, voice, video, sound, gaming, or substantially anydata-stream or signaling-stream to and from a set of subscriber stationsor provider enabled devices. Data and signaling streams can includepacketized or frame-based flows.

Additionally, the terms “core-network”, “core”, “core carrier network”,“carrier-side”, or similar terms can refer to components of atelecommunications network that typically provides some or all ofaggregation, authentication, call control and switching, charging,service invocation, or gateways. Aggregation can refer to the highestlevel of aggregation in a service provider network wherein the nextlevel in the hierarchy under the core nodes is the distribution networksand then the edge networks. UEs do not normally connect directly to thecore networks of a large service provider but can be routed to the coreby way of a switch or radio access network. Authentication can refer todeterminations regarding whether the user requesting a service from thetelecom network is authorized to do so within this network or not. Callcontrol and switching can refer determinations related to the futurecourse of a call stream across carrier equipment based on the callsignal processing. Charging can be related to the collation andprocessing of charging data generated by various network nodes. Twocommon types of charging mechanisms found in present day networks can beprepaid charging and postpaid charging. Service invocation can occurbased on some explicit action (e.g. call transfer) or implicitly (e.g.,call waiting). It is to be noted that service “execution” may or may notbe a core network functionality as third party network/nodes may takepart in actual service execution. A gateway can be present in the corenetwork to access other networks. Gateway functionality can be dependenton the type of the interface with another network.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“prosumer,” “agent,” and the like are employed interchangeablythroughout the subject specification, unless context warrants particulardistinction(s) among the terms. It should be appreciated that such termscan refer to human entities or automated components (e.g., supportedthrough artificial intelligence, as through a capacity to makeinferences based on complex mathematical formalisms), that can providesimulated vision, sound recognition and so forth.

Aspects, features, or advantages of the subject matter can be exploitedin substantially any, or any, wired, broadcast, wirelesstelecommunication, radio technology or network, or combinations thereof.Non-limiting examples of such technologies or networks include broadcasttechnologies (e.g., sub-Hertz, extremely low frequency, very lowfrequency, low frequency, medium frequency, high frequency, very highfrequency, ultra-high frequency, super-high frequency, terahertzbroadcasts, etc.); Ethernet; X.25; powerline-type networking, e.g.,Powerline audio video Ethernet, etc; femto-cell technology; Wi-Fi;worldwide interoperability for microwave access; enhanced general packetradio service; third generation partnership project, long termevolution; third generation partnership project universal mobiletelecommunications system; third generation partnership project 2, ultramobile broadband; high speed packet access; high speed downlink packetaccess; high speed uplink packet access; enhanced data rates for globalsystem for mobile communication evolution radio access network;universal mobile telecommunications system terrestrial radio accessnetwork; or long term evolution advanced.

What has been described above includes examples of systems and methodsillustrative of the disclosed subject matter. It is, of course, notpossible to describe every combination of components or methods herein.One of ordinary skill in the art may recognize that many furthercombinations and permutations of the claimed subject matter arepossible. Furthermore, to the extent that the terms “includes,” “has,”“possesses,” and the like are used in the detailed description, claims,appendices and drawings such terms are intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim.

What is claimed is:
 1. A service device, comprising: a processor; and amemory that stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising: receiving,from a vehicle device of a vehicle, a representation of contentinformation that is encrypted according to a key value to enable securedsharing of the representation of the content information with theservice device, wherein the representation of the content information isdetermined by a mobile device that is different from the service deviceand the vehicle device, and wherein the service device is locatedproximate to the vehicle and the mobile device; and in response todecrypting the representation of the content information based on therepresentation of the content information and the key value, initiatingaccess to a determined account.
 2. The service device of claim 1,wherein the key value is separately received from the mobile device. 3.The service device of claim 2, wherein the key value is received inresponse to an input determined to be associated with a user identity.4. The service device of claim 3, wherein the input is received inresponse to querying the mobile device for the key value.
 5. The servicedevice of claim 1, wherein the representation is an electronicrepresentation and the sharing is via a radio frequency wirelessinterface, and wherein the service device being proximate to the vehicleis the service device being within a distance allowing the servicedevice to receive a radio frequency signal from the vehicle device viathe radio frequency wireless interface.
 6. The service device of claim1, wherein the sharing is via an infrared wireless interface, andwherein the service device being proximate to the vehicle is the servicedevice being within a distance allowing the service device to receive aninfrared signal from the vehicle device via the infrared wirelessinterface.
 7. The service device of claim 1, wherein the representationis a tonal representation and the sharing is via an audio signalgenerated by the vehicle, and wherein the service device being proximateto the vehicle is the service device being within a distance allowingthe service device to receive the audio signal from the vehicle device.8. The service device of claim 7, wherein the audio signal has beengenerated by the vehicle via an audio system comprising a speakerdevice.
 9. The service device of claim 1, wherein the representation isa visual representation and the sharing is via generation of an imagevia an image display device of the vehicle, and wherein the servicedevice being proximate to the vehicle is the service device being withina distance allowing the service device to receive the image from thevehicle device via the image display device.
 10. The service device ofclaim 9, wherein the generation of the image comprises generation of abar code image.
 11. The service device of claim 9, wherein thegeneration of the image comprises generation of a matrix bar code image.12. The service device of claim 1, wherein the sharing comprisesgeneration of an optical signal by an optical device of the vehicle. 13.The service device of claim 12, wherein the generation of the opticalsignal comprises pulsing a headlight device.
 14. A method, comprising:receiving, by a service device comprising a processor, a representationof account information from a vehicle device, wherein the representationof account information comprises encrypted account information and isdetermined by a mobile device that is different from the service deviceand the vehicle device, wherein the service device is located proximateto a vehicle comprising the vehicle device and is located proximate tothe mobile device, and wherein the representation of account informationand a key value are together employable by the service device todetermine the account information; and in response to determining, bythe service device, the account information based on the representationof account information and the key value, accessing an accountcorresponding to the account information.
 15. The method of claim 14,further comprising receiving, by the service device separately from thereceiving the representation of account information, the key value viathe mobile device.
 16. The method of claim 14, wherein the receiving bythe service device is in response to the mobile device receiving anexternal input.
 17. The method of claim 14, wherein the receiving theaccount information occurs in response to a query from the servicedevice.
 18. A non-transitory machine-readable storage medium, comprisingexecutable instructions that, when executed by a processor, facilitateperformance of operations, comprising: receiving, by a service devicecomprising the processor, a representation of content information from avehicle device, wherein the representation comprises the contentinformation encrypted based on a key value, wherein the representationis determined by a mobile device and provided to the vehicle device bythe mobile device for communication to the service device, wherein theservice device is located proximate to a vehicle comprising the vehicledevice and also proximate to the mobile device, and wherein the contentinformation comprises account information; and accessing the contentinformation based on decrypting the representation based on the keyvalue.
 19. The non-transitory machine-readable storage medium of claim18, wherein the key value is received by the processor separately fromthe receiving the representation.
 20. The non-transitorymachine-readable storage medium of claim 19, wherein the receiving therepresentation is performed in response to a query from the servicedevice.